| Version 6 (modified by , 17 years ago) (diff) |
|---|
Using Libpurple
Why do libPurple clients store settings and logs in ~/.purple?
When creating libPurple under a separate name from Pidgin, the first client to use it, we were faced with a choice. We could have Pidgin store in ~/.pidgin, Finch in ~/.finch, and any other future clients in ~/.clientname. This would create significant duplication for those who sometimes use different clients, or who migrate from one client to another but do not remove the old directory. It would also make things like logs more complex, as there would be no built-in single place to store logs. Someone using both Pidgin and Finch, or migrating from Pidgin to Finch (or back), no doubt expects all of their logs to be read by both. The other alternative was to have all libPurple based clients use ~/.purple by default. Though the client author can naturally chose some other directory, having this as a default seems to make the most sense. Much of the content of ~/.purple would be usable by any libPurple based client, and those things that are not useful to all clients can be detected and ignored using the existing API. While we have not yet handled the case of running multiple libPurple based clients at the same time (as the same user, and not using a -c flag or equivalent), we plan to in the future.
Why are passwords not encrypted?
See PlainTextPasswords.
What do I need to use the SILC protocol?
You need to install the
SILC toolkit and the Pidgin SILC plugin. This plugin is generally provided as a separate package (such as a purple-silc RPM). If you're compiling yourself, see the ./configure --help for specifying the SILC includes and libs. If you're compiling an SRPM, use --with silc to build the purple-silc RPM.
In Windows, the SILC toolkit is installed with Pidgin.
Some distributions provide the SILC toolkit and include Pidgin's SILC plugin in their Pidgin package.
